home *** CD-ROM | disk | FTP | other *** search
- Path: news.fast.net!news
- From: alf <alf@fast.net>
- Newsgroups: comp.dcom.modems,alt.winsock,yale.users.windows95,comp.os.ms-windows.setup.win95,comp.os.ms-windows.win95.setup,comp.os.ms-windows.win95.misc
- Subject: Re: Win95 Modem problem: HELP! (please)
- Date: 19 Jan 1996 05:08:58 GMT
- Organization: FASTNET(tm) PA/NJ/DE Internet
- Message-ID: <4dn91a$fk7@nn.fast.net>
- NNTP-Posting-Host: abe-ppp322.fast.net
-
- stout@minerva.ycc.yale.edu (R. G. Stout) writes:
- > Thanks for your input! I have worked around the problem (without
- > changing modem drivers) by using the ATM3 command (the speaker emits a
- > very quick dial-tone sound, then silence, then negotiating tones). This
- > is somewhat of a kludge since I want the speaker to stay on from dial
- > tone until the end of negotiation, but it will do. I'll search for the
- > ";" dial suffix in the registry and eliminate it to see if that works.
- >
- > -Bob Stout
- > Robert.Stout@Yale.Edu
- > ]I do not know for sure but give it a try. My experience wirh modems
- > ]and Windows 95 was the ATD; part. WIN 95 waits for an OK but most
- > ]modems wait for the next string to come. In one of my environments
- > ](A microcom modem) I deleted the ';' from the registry. You may find
- > ]it in the registry under 'dial_suffix' or something like that. Just do
- > ]a search on suffix and you will find it.
- > ]
- > ]Enable modem log will help. Experts can tell very soon from the log
- > ]what is happening.
- > ]
- > ]Hope this helps,
- > ]
- > ]
- > ]
- > ]Arie Lodder
- > ]Numansdorp, The Netherlands
- > ]alodder@luna.nl
- >
- >
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- _set your CMOS to default, than:
- _check out your CMOS first, make sure your COM 1 and 2
- ports set up to 'AUTO'(in order for your hardware IRQ
- addresses didn't confront with modem software IRQ
- addresses)
- _make sure you didn't forget to check 'plug and play'
- features in your CMOS.
- _if you have even an internal modem, connect it to Com2, at
- least, give it a shot.
- _run hardware setup
-
- It should work.
-
-
-
-
-